chore: store pom version as resource property and use it for capabili…#292
Merged
chore: store pom version as resource property and use it for capabili…#292
Conversation
Contributor
|
@jeremnaf I cannot rebase, there are conflicts to handle |
b2e2ef8 to
35f1624
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ty template
Related Issue
Closes #176
What does this PR do?
Don't be afraid! The majority of modified files are just an update from 1.0.0-alpha1 to 1.0.0-alpha2.
Real updates are:
Tests
Update all existing tests with the version number of the pom.xml.
Checklist
mainAgent Context (optional)